Visit a page
Click a link/button
Verify the new URL
Assert content on the new page
Click Button That Navigates
Navigate via JS or Redirect
Imagine you need to verify that clicking the 'Login' button on the homepage takes the user to '/login'. How would you write a Cypress test for that?
If the navigation fails intermittently, what simple Cypress command could you add to make the test more reliable?
You have a multi‑step wizard where each step updates the URL hash. How would you assert that moving from step 2 to step 3 updates the hash correctly, and what would you do if the hash sometimes lags behind?
During a recent sprint, a teammate reported that a Cypress test for navigating to the 'Settings' page started failing after a new API call was added. Walk me through how you'd debug the failure.
Our application uses lazy‑loaded modules and sometimes the navigation test times out. How would you redesign the Cypress navigation tests to be resilient at scale, considering network stubbing and retries?
We plan to run Cypress tests in parallel across multiple CI agents. What considerations would you make for navigation tests to avoid flaky results and keep execution time low?
The company is moving from a monolithic Cypress suite to a modular, shared component library for tests. How would you structure navigation test utilities to support multiple teams while maintaining consistency?
If we need to migrate legacy Selenium navigation tests to Cypress across dozens of services, what strategy would you propose to ensure coverage, minimize risk, and handle differing routing implementations?